Hacking Switching CFW and in what concerns cheats?

[Itachi.Brando]

Greetings everyone,
So I want to change my CFW,and instead of using CakesFW,I want to use rxTools' for these reasons mainly:
Playing GBA and DSi games.
With my CakesFW,I cannot do so. Yesterday I downloaded and followed steps on how to install rxTools and unlink everything, and it was successful and GBA games work just fine. However,my issue is with my games on my Cakes. I have been using Cakes for some six months,and so, I made a great progress with several different games such as Pokémon and DOA: Dimensions etc...
If I am going to switch to rxTools,I am going to lose my save files I believe?

Is there any way to backup or extract my saves so that if I install the games on rxTools emuNand I would be able to resume them? Any requires tools/software?
And in what concerns cheats,is there any app that allows that? (No Gateway)

 

[The Real Jdbye]

Greetings everyone,
So I want to change my CFW,and instead of using CakesFW,I want to use rxTools' for these reasons mainly:
Playing GBA and DSi games.
With my CakesFW,I cannot do so. Yesterday I downloaded and followed steps on how to install rxTools and unlink everything, and it was successful and GBA games work just fine. However,my issue is with my games on my Cakes. I have been using Cakes for some six months,and so, I made a great progress with several different games such as Pokémon and DOA: Dimensions etc...
If I am going to switch to rxTools,I am going to lose my save files I believe?

Is there any way to backup or extract my saves so that if I install the games on rxTools emuNand I would be able to resume them? Any requires tools/software?
And in what concerns cheats,is there any app that allows that? (No Gateway)

You won't lose your saves and you can use cheats with NTR-CFW.
But I think rxTools won't work with high memory mode games like Smash Bros and Monster Hunter because the reboot patch isn't the newer version that Cakes and Luma use which supports both gba/dsiware and high memory mode games.
In Cakes this patch has to be enabled and as long as you're on a recent enough version those things should work fine. In Luma it works out of the box. I recommend switching to Luma and staying away from rxTools since it's obsolete.

 

[TheReturningVoid]

Luma3DS is the recommended CFW at the moment. It can play GBA and DSi games. Information on how to set it up can be found here.

 

[Davidosky99]

No, you'll not lose saves. Never touch rxtools like ever, use luma3ds , rxtools is DEAD ,it's not reliable its unstable, no one supports it anymore and compared to luma3ds its shit.
Use luma3ds instead. You won't lose anything. It's easy

 

[sirocyl]

You will not lose save files because those are stored in the save area for those titles in your SD card.
You can backup and extract those saves using svdt or JKSM or similar save managers.
Cheats can be done with NTR CFW, but not in GBA or DSi games.

I'd also recommend you use Luma3DS - it's got all the features rxTools has, but it's constantly up to date. I don't think RxTools supports 11.x firmware, for instance.

 

[Itachi.Brando]

Too much appreciated,everyone!

--------------------- MERGED ---------------------------

Luma3DS is the recommended CFW at the moment. It can play GBA and DSi games. Information on how to set it up can be found here.

I am following that right now.
I just have one question. I found that there is an EmuNAND9 folder and boot file as well. So when I am copying my old files back on the SD,should I overwrite or skip them?

 

[TheReturningVoid]

Too much appreciated!

--------------------- MERGED ---------------------------


I am following that right now.
I just have one question. I found that there is an EmuNAND9 folder and boot file as well. So when I am copying my old files back on the SD,should I overwrite or skip them?

Skip.

 

[Luglige]

Just use Luma. Before I bricked my 2ds I used rxTools. I do like the UI of rxTools though. It looks nice.

 

[dahacker2017]

You will not lose save files because those are stored in the save area for those titles in your SD card.
You can backup and extract those saves using svdt or JKSM or similar save managers.
Cheats can be done with NTR CFW, but not in GBA or DSi games.

I'd also recommend you use Luma3DS - it's got all the features rxTools has, but it's constantly up to date. I don't think RxTools supports 11.x firmware, for instance.

actually it does

 

[astronautlevel]

actually it does

But it won't support 11.1, and today is Nintendo update day

 

[dahacker2017]

But it won't support 11.1, and today is Nintendo update day

actually it does lol just tested

 

[astronautlevel]

actually it does lol just tested

Your reading comprehension level: 0

"It won't support 11.1" - I'm saying that once Nintendo updates any system application it will break rxTools. Maybe read what someone is saying, or learn about how the system works, before saying "lol" in response to somebody's post.

 

[The Real Jdbye]

Your reading comprehension level: 0

"It won't support 11.1" - I'm saying that once Nintendo updates any system application it will break rxTools. Maybe read what someone is saying, or learn about how the system works, before saying "lol" in response to somebody's post.

That's not exactly true. rxTools will only stop working if they change something that makes the new firmware incompatible with older FIRM versions. That would be a rather major change and there hasn't been one of those since 9.6. The 3DS is nearing the end of its life so there may never be another one of those updates.
There are plenty of other reasons not to use rxTools, though.

 

[dahacker2017]

That's not exactly true. rxTools will only stop working if they change something that makes the new firmware incompatible with older FIRM versions. That would be a rather major change and there hasn't been one of those since 9.6. The 3DS is nearing the end of its life so there may never be another one of those updates.
There are plenty of other reasons not to use rxTools, though.

nice job

 

[astronautlevel]

That's not exactly true. rxTools will only stop working if they change something that makes the new firmware incompatible with older FIRM versions. That would be a rather major change and there hasn't been one of those since 9.6. The 3DS is nearing the end of its life so there may never be another one of those updates.
There are plenty of other reasons not to use rxTools, though.

11.0 already updated MINOR_VERSION, so any (important) system app updated will break rxTools.

--------------------- MERGED ---------------------------

nice job

On one hand I want to explain to you why you're so wrong, on the other hand I'm in a good mood and don't want to ruin it.

I'll just leave this here instead: https://www.3dbrew.org/wiki/FIRM#NATIVE_FIRM

 

[The Real Jdbye]

11.0 already updated MINOR_VERSION, so any (important) system app updated will break rxTools.

That's not how it works. The version does nothing at all. What matters is what is updated.
rxTools only patches NATIVE_FIRM (which is all that is needed for basic signature check patching and region free), as well as AGB_FIRM and TWL_FIRM (which are not really needed unless you want to run GBA injects/outdated DS flashcarts)
The rest of the firmware runs as-is. So as long as the new firmware is compatible with the FIRM version that rxTools uses, it will keep working.
GBA/DSiWare however will not run alongside extended memory mode games like Monster Hunter and Smash 4 on o3DS due to rxTools using an old reboot patch that did not support both at the same time. As I was saying there are plenty of other reasons not to use rxTools. They don't prevent the CFW from functioning though.

 

[The Catboy]

Do not use RXTools there are better options
http://gbatemp.net/threads/wip-faq-what-cfw-is-best-for-me.428509/

And you can switch between cfw's without effecting your NAND as your CFW is only a means of reading the NAND and not writing to it. You can even run multiple CFW's without hassle, I know because I am running 6 of them right now on my sysNAND.

 

[astronautlevel]

Sigh. I love it when people who have no idea what they're talking about "call me out" on Temp, because it means that I get to write a lengthy response. Weeeee.

That's not how it works. The version does nothing at all. What matters is what is updated.

Nope, you're wrong. The kernel version is stored as KERNEL_VERSIONMAJOR.KERNEL_VERSIONMINOR-KERNEL_VERSIONREVISION. All system applications perform a version check, and if the KERNEL_VERSIONMINOR is outdated then they refuse to launch. If you're interested, this version check is in the exheader. As a result, when KERNEL_VERSIONMINOR gets updated we can't firmlaunch old versions, as important system applications (such as home menu or ErrDisp) won't launch. The last time this happened before 11.0 was 9.6 (which, coincidentally, is why we can't launch older than 9.6 on 9.6+). For every NFIRM update since 9.6 they only updated KERNEL_VERSIONREVISION, until 11.0 which bumped us from 2.50-11 to 2.51-0. The only reason we can still firmlaunch 10.2/9.6 NFIRM is because no system applications have been updated to check for the new NFIRM version.

rxTools only patches NATIVE_FIRM (which is all that is needed for basic signature check patching and region free), as well as AGB_FIRM and TWL_FIRM (which are not really needed unless you want to run GBA injects/outdated DS flashcarts)

Irrelevant to the discussion.

The rest of the firmware runs as-is. So as long as the new firmware is compatible with the FIRM version that rxTools uses, it will keep working.

Wrong, see above.

GBA/DSiWare however will not run alongside extended memory mode games like Monster Hunter and Smash 4 on o3DS due to rxTools using an old reboot patch that did not support both at the same time. As I was saying there are plenty of other reasons not to use rxTools. They don't prevent the CFW from functioning though.

This is accurate.

11.1 will likely update an important system title, whether that's Home Menu, ErrDisp, or really anything else (they all get updated frequently enough), so if that happens it's game over for old firmlaunches and it's game over for rxTools.

 

[The Real Jdbye]

Sigh. I love it when people who have no idea what they're talking about "call me out" on Temp, because it means that I get to write a lengthy response. Weeeee.



Nope, you're wrong. The kernel version is stored as KERNEL_VERSIONMAJOR.KERNEL_VERSIONMINOR-KERNEL_VERSIONREVISION. All system applications perform a version check, and if the KERNEL_VERSIONMINOR is outdated then they refuse to launch. If you're interested, this version check is in the exheader. As a result, when KERNEL_VERSIONMINOR gets updated we can't firmlaunch old versions, as important system applications (such as home menu or ErrDisp) won't launch. The last time this happened before 11.0 was 9.6 (which, coincidentally, is why we can't launch older than 9.6 on 9.6+). For every NFIRM update since 9.6 they only updated KERNEL_VERSIONREVISION, until 11.0 which bumped us from 2.50-11 to 2.51-0. The only reason we can still firmlaunch 10.2/9.6 NFIRM is because no system applications have been updated to check for the new NFIRM version.


Irrelevant to the discussion.


Wrong, see above.


This is accurate.

11.0 will likely update an important system title, whether that's Home Menu, ErrDisp, or really anything else (they all get updated frequently enough), so if that happens it's game over for old firmlaunches and it's game over for rxTools.

Changes to the kernel version go under "as long as the new firmware is compatible with the FIRM version".
I don't see where I was wrong.
And "we can't launch older than 9.6 on 9.6+"? What do you mean by that? Launching older emuNAND on 9.6+ FIRM? Because that works just fine.

 

[astronautlevel]

Changes to the kernel major version go under "as long as the new firmware is compatible with the FIRM version".
I don't see where I was wrong.

Where the fuck did I say that?

Allow me to reiterate: All system applications check the kernel version. They ignore revision version. Minor version got updated in 11.0 so version check will fail once any system application updates to check for the new version, causing old firmlaunches (such as rxTools) to break.