Hi,
I have currently a Gateway since my Sky3ds V2 isn't usable anymore with the recent games.
Since I have bought the GW, I'm learning how to use it and what I can do with it.
It's amazing.
But now I dig a little I see there is CFW.
So which is best ? GW or CFW ?
If GW, how can I easily boot to emuNand (the method describe in the manual is not very user friendly and take time) ? Coldboot ? And how can I boot classic emuNand in order to play my retail cardridge ?
If CFW, which one ?
I've got a new 3ds XL with firmware 9.2. And a 16gb sd card. I can put a 32 or maybe 64gb if needed.
Thank you for your help.
Gateway is basically CFW with some extra features, if you don't want/need a9lh, GW is an improvement over other CFW. It includes several features that are not possible with CFW like firmware spoofing, a realtime cheat editor, loading .3DS roms and so on.
.3DS roms are easier/faster to use because you can just copy it on to the cart and play, no need for lengthy install processes.
Thanks for your response.
If I choose to cold boot with MenuHax, will it take longer time to boot than the stock firmware ?
And if I chose this solution, the Gateway.3dsx file will show me the GW menu and I will be able to chose between emuNand and classic emuNand ?
If the boot time is not too long and 100% successfull it could be a solution.
GW + Arm9LoaderHax could be another solution ?
About the CFW, there is too many of them and too few informations about what are the functionnality.
You talk about AuReiNand, I thought this was a CFW that only patch sysNand and doesn't support emuNand ...
Is there somewhere something that sum up the functionnality and the fact that the CFW is still alive ?
I must tell something : I don't want to loose any data in the process and during the usage of my configuration.
In addition I think I will do some regular backup in order to minimize the loss of data in case of problem.
Again many thanks.
It takes longer to boot than stock firmware, but it's the fastest way of booting Gateway, and the success rate is very high, probably 90%+
AuReiNand works with emuNAND as well as sysNAND, but it's the preferred CFW for a9lh, which is why many people use it with a9lh+sysNAND.
Most CFW are very similar feature-wise but a9lh offers a couple more features than other CFW, especially when using a9lh since it offers a bunch of a9lh-specific features. Whether using *hax or a9lh AuReiNAND is still a very good option though.
You won't lose any data no matter what you do, since you already have emuNAND set up (I'm assuming since you're using Gateway) you can just keep using that same emuNAND with any CFW.
I'm in the same situation as you. I have 2 O3DSes. They're both on 9.2 SysNAND and 10.7 EmuNAND. I use Gateway and I have Menuhax installed on both. That currently seems like the easiest setup, but everyone says to look into Arm9 because it actually hacks your SysNAND, so you don't even need EmuNAND for it (You can still use EmuNAND with O3DS, not N3DS, because EmuNAND bricks when you try to get the OTP file needed for Arm9 according to the guide), Arm9 boots a lot faster than Menuhax, and you can also update your SysNAND with it without really risking being locked out of hacks.
AuReiNAND is definitely still alive as it is very new, and everyone says it is currently the best setup with Arm9, AuReiNAND, and NTR. AuReiNAND doesn't have region free patching though, so you install it with NTR (which is a CFW that you install with any CFW you want) to get region free patching, you also get the perk of cheat plugins with NTR amongst others. I'm currently debating whether I should do ARM9 with AuRei and NTR, because I still want to use my Gateway card as I still have a 32GB microSD card in there, but I've heard that Gateway clashes with that setup.
You can certainly use emuNAND with either o3DS or n3DS with a9lh installed. You just can't boot a 2.1 emuNAND, CFW is simply unable to boot a 2.1 emuNAND because they were designed for 4.x+ and 2.1 firmware is very different from newer firmwares.
I'd say CFW. I wouldn't trust GW. They've put in brick code that even gets false positives and bricks actual GW users TWICE NOW. I wouldn't be surprised if it's still hidden in there.
There have been no false positives since the version where it was implemented. (which was in 2.2 or around there)
1) That makes it right?
2) What about the false positives that brick with the GW card?
There were a few confirmed cases of people using a legit GW cart getting bricked, and it turned out it was mainly a bug in the diagnostics test that caused it. It shouldn't have happened, but it wasn't intentional on GW's part, it was a bug in their brick code. Make of that what you will.